fix(seo): canonical points to /chains/<slug> when provider IS a chain - #758
Merged
Conversation
/products/eth-usd, /products/bnb-usd, /products/avalanche-official etc. resolve to a canonical provider whose slug matches a chain (ethereum, bnb, avalanche...). The previous canonical /products/<chain> then 308s to /chains/<chain>, so Ahrefs + GSC flag 'canonical points to redirect' and Google may split rank instead of consolidating on the final URL. Now we check the chain registry and short-circuit the canonical (+ OG url) straight to /chains/<slug> for chain-shaped providers. Non-chain providers (helius, dRPC, mobula) keep /products/<slug>.
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Ahrefs flagged 10 `/products/` pages whose canonical points to a redirect:
Canonical → 308 → 200 is a confused signal — Google may ignore the canonical and split rank between source + final URL instead of consolidating on the chain hub.
Fix
`generateMetadata` in `products/[slug]/page.tsx` now checks `CHAIN_BY_SLUG` and points canonical (+ OG url) directly to `/chains/` when the resolved provider IS a chain. Non-chain providers (helius, dRPC, mobula, etc.) keep `/products/` as before.
Test plan after deploy